-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support actions in publishChecks Step #85
Conversation
Codecov Report
@@ Coverage Diff @@
## master #85 +/- ##
============================================
+ Coverage 86.82% 87.21% +0.38%
- Complexity 140 142 +2
============================================
Files 16 16
Lines 630 649 +19
Branches 49 49
============================================
+ Hits 547 566 +19
Misses 65 65
Partials 18 18
Continue to review full report at Codecov.
|
2e966f5
to
88f492a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't there be some docs updates? or help file updates?
src/main/java/io/jenkins/plugins/checks/steps/PublishChecksStep.java
Outdated
Show resolved
Hide resolved
a4f5d37
to
950ac92
Compare
Can you try avoid force pushing while under review please, it makes it harder for me to tell what changed so I have to review from the beginning |
src/main/java/io/jenkins/plugins/checks/steps/PublishChecksStep.java
Outdated
Show resolved
Hide resolved
...ces/io/jenkins/plugins/checks/steps/PublishChecksStep/StepChecksAction/help-description.html
Outdated
Show resolved
Hide resolved
...rces/io/jenkins/plugins/checks/steps/PublishChecksStep/StepChecksAction/help-identifier.html
Outdated
Show resolved
Hide resolved
src/main/resources/io/jenkins/plugins/checks/steps/PublishChecksStep/config.jelly
Outdated
Show resolved
Hide resolved
src/test/java/io/jenkins/plugins/checks/steps/PublishChecksStepITest.java
Outdated
Show resolved
Hide resolved
src/test/java/io/jenkins/plugins/checks/steps/PublishChecksStepTest.java
Outdated
Show resolved
Hide resolved
@@ -118,6 +118,12 @@ | |||
<versionFormat>\d+\.\d+\.\d+</versionFormat> | |||
<analysisConfiguration> | |||
<revapi.ignore combine.children="append"> | |||
<item> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this still needed? I think you adjusted the implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, still needed, since we still add new field to PublishChecks
step.
[INFO] API problems found.
[INFO] If you're using the semver-ignore extension, update your module's version to one compatible with the current changes (e.g. mvn package revapi:update-versions). If you want to explicitly ignore these changes or provide justifications for them, add the json snippets to your Revapi configuration for the "revapi.differences" extension.
{
"code": "java.field.serialVersionUIDUnchanged",
"old": "field io.jenkins.plugins.checks.steps.PublishChecksStep.serialVersionUID",
"new": "field io.jenkins.plugins.checks.steps.PublishChecksStep.serialVersionUID",
"serialVersionUID": "1",
"justification": "ADD YOUR EXPLANATION FOR THE NECESSITY OF THIS CHANGE"
/* "package": "io.jenkins.plugins.checks.steps",
"classQualifiedName": "io.jenkins.plugins.checks.steps.PublishChecksStep",
"classSimpleName": "PublishChecksStep",
"fieldName": "serialVersionUID",
"elementKind": "field",
"oldArchive": "io.jenkins.plugins:checks-api:hpi:1.5.0",
"oldArchiveRole": "primary",
"newArchive": "io.jenkins.plugins:checks-api:hpi:1.6.0-SNAPSHOT",
"newArchiveRole": "primary",
"breaksSemanticVersioning": "true",
*/
},
Co-authored-by: Tim Jacomb <[email protected]>
Sorry, my bad 😅 |
Solve issue: #74